Hvac system configuration and zone management

ABSTRACT

Systems and methods for HVAC system design and zone group management are disclosed. A floor plan of a building is received, and an HVAC system configuration is selected from among a set of template HVAC configurations. HVAC components are selected from set of template HVAC components to customize the configuration. As components are selected, candidate positions for the HVAC component within the HVAC system configuration are determined and presented to a user to ensure compliance with engineering requirements. The floor plan includes a mapping of an HVAC system configuration to an HVAC zone group. If a change is made to the HVAC system configuration of a zone associated with a zone group, it is determined if another zone group shares the same properties as the changed HVAC configuration. If one exists, the changes]d zone is moved to the new zone group. If not, a new zone group is created and the changes zone is moved to the new zone group.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of and priority to U.S. ProvisionalApplication Ser. No. 62/451,742 entitled “HVAC SYSTEM CONFIGURATION ANDZONE MANAGEMENT” and filed Jan. 29, 2017, the entirety of which ishereby incorporated by reference herein for all purposes.

BACKGROUND 1. Technical Field

The present disclosure is directed to modeling and designing complexHVAC systems, and in particular, to systems and methods for simulatingHVAC component sizing, energy consumption, and economic factors tooptimize HVAC component selections and interconnections used toconfigure an HVAC system.

2. Background of Related Art

HVAC system installations can range from residential systems whichtypically have an outdoor unit and an indoor unit connected by a singlerefrigerant circuit, and controlled by a single thermostat, tocommercial systems which may include multiple variable air volume (VAV)boxes, chiller plants, rooftop units, variable refrigerant flow (VRF)systems, and convectors under the control of a highly customizedbuilding automation system (BAS). Considerable resources and technicalexpertise are required to design and build an HVAC system, particularlyin the case of commercial buildings having many rooms which may havedifferent climate control requirements. Modern HVAC systems are expectedto be efficient, flexible, and meet rigid energy usage requirements.HVAC system requirements may differ based on the local climate andzoning regulations. As a result, computer-implemented HVAC design andmodeling methods have been employed to assist the HVAC design engineerin planning, designing, specifying, and installing an HVAC system. Suchsystems may have drawbacks because as the number of HVAC components usedin the system increases, the design decisions faced by the designengineer while keeping track of the many technical requirements of eachcomponent quickly becomes unmanageable, leading to a non-optimal design.An HVAC design and modeling tool that provides useful, improved featuresin an efficient and easy-to-use manner would be a welcome advance.

SUMMARY

In one aspect the present invention is directed to a method forconstructing an HVAC system for a structure, such as a building, havingdistinct thermal zones. The method defining the structure and definingan HVAC topology included in the structure. Common elements of the HVACtopology associated with a distinct thermal zone are identified, and azone group comprising distinct zones sharing similar common elements andthermal properties is defined. The zone group is modified if at leastone distinct zone of the zone group no longer shares common elementswith at least one other distinct zone of the zone group. A set of HVACparameters for the structure is generated.

In some embodiments, defining the HVAC topology included in thestructure includes defining one or more HVAC components included in thestructure. In some embodiments, defining an HVAC topology included inthe structure includes defining an interconnection between one or moreHVAC components included in the structure. In some embodiments, themodifying the zone group includes removing from the zone group thedistinct zone that no longer shares common elements with at least oneother distinct zone of the zone group, and adding the removed distinctzone to a different zone group comprising distinct zones sharing similarcommon elements with the removed distinct zone. In some embodiments,defining an HVAC topology included in the structure includes providing aset of pre-defined characteristics of an HVAC component, wherein thepre-defined characteristics include a configuration rule and asimulation rule. A representation of a distinct thermal zone is insertedinto a zone tree. The HVAC component is joined to at least one otherHVAC component in the distinct thermal zone, if any, based upon thepre-defined characteristics of the respective HVAC components. In someembodiments, the set of pre-defined characteristics of an HVAC componentare expressed in an extensible markup language. In some embodiments,inserting the representation into a zone tree representative of adistinct thermal zone includes storing the configuration rule and thesimulation rule in third normal form.

In another aspect, a method for constructing an HVAC system model of astructure having distinct thermal zones is disclosed. The methodincludes defining the structure, defining a plurality of HVAC componentsincluded in the structure, defining interconnections between two or moreof the plurality of HVAC components included in the structure,identifying a further HVAC component to be inserted into aninterconnection of the structure, and identifying a candidateinterconnection into which the further HVAC component may be inserted.

In yet another aspect, method for manipulating HVAC systemconfigurations is disclosed. The method includes displaying a pluralityof HVAC system configurations in a viewer executing on an electronicdevice having a graphic display, receiving, at the electronic device, auser selection of HVAC system configuration displaying the selected HVACsystem configuration in the viewer displaying a plurality of HVACcomponents in the viewer; receiving, at the electronic device, a userselection of a HVAC component applying a rules-based engine to determinethe possible locations within the HVAC system configuration where theselected HVAC component may be placed; and displaying the possiblelocations the selected HVAC component may be placed on the HVAC systemconfiguration in the viewer.

In still another aspect, the present disclosure is directed to acomputer-implemented method for configuring a heating, ventilation, andair conditioning (HVAC) system of a building. The method includesreceiving, by a processor, a floor plan of the building; receiving, bythe processor, an HVAC system configuration selected from among a set oftemplate HVAC configurations; receiving, by the processor, an HVACcomponent selected from among a set of template HVAC components;determining, by the processor, a candidate position for the HVACcomponent within the HVAC system configuration; and displaying, on avisual display in communication with the processor; the candidateposition for the HVAC component on a schematic diagram of the HVACsystem configuration.

In a further aspect, the present disclosure is directed to acomputer-implemented method for configuring a heating, ventilation, andair conditioning (HVAC) system of a building, comprising receiving, by aprocessor, a floor plan of the building, wherein the floor plan includesa mapping of an HVAC system configuration to a first HVAC zone group;receiving, by the processor, a change to the HVAC system configurationassociated with a first HVAC zone of the first HVAC zone group;determining, by the processor, whether a second HVAC zone group ismapped to a system configuration having the same properties as thechanged HVAC configuration of the first zone. In some embodiments, thecomputer-implemented method includes responding to a determining that asecond HVAC zone group is mapped to a system configuration having thesame properties as the changed HVAC configuration of the first zone byremoving the first zone from the first HVAC zone group and adding thefirst zone to the second HVAC zone group. In some embodiments, thecomputer-implemented method includes responding to a determining that asecond HVAC zone group is not mapped to a system configuration havingthe same properties as the changed HVAC configuration of the first zoneby removing the first zone from the first HVAC zone group, creating anew HVAC zone group, and adding the first zone to the new HVAC zonegroup. in some embodiments, the computer-generated method includesautomatically assigning a new name to the new HVAC zone group. In someembodiments, the computer-generated method includes displaying, on avisual display in communication with the processor; zone of the new zonegroup using a different visual representation from that of the firstzone group. A different visual representation includes a displaying in adifferent color, a different hatching, and/or a different backgroundimage.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the disclosed system and method are describedherein with reference to the drawings wherein:

FIG. 1 depicts a system configurator in accordance with an exemplaryembodiment of the present disclosure;

FIG. 2 depicts a system configurator in accordance with an exemplaryembodiment of the present disclosure showing a system schematic diagram;

FIG. 3 depicts a system configurator in accordance with an exemplaryembodiment of the present disclosure showing candidate device positions;

FIG. 4 depicts a system configurator in accordance with an exemplaryembodiment of the present disclosure showing a system modification inplace;

FIG. 5 depicts a system configurator in accordance with an exemplaryembodiment of the present disclosure showing additional systemmodifications in place;

FIG. 6 depicts a system configurator in accordance with an exemplaryembodiment of the present disclosure showing control connections;

FIG. 7 depicts a system configurator in accordance with an exemplaryembodiment of the present disclosure showing further controlconnections;

FIG. 8 depicts a zone group manager in accordance with an exemplaryembodiment of the present disclosure;

FIG. 9 depicts a zone group manager in accordance with an exemplaryembodiment of the present disclosure showing a new component selection;

FIG. 10 depicts a zone group manager in accordance with an exemplaryembodiment of the present disclosure showing automatic zone groupcreation;

FIG. 11 depicts a zone group manager in accordance with an exemplaryembodiment of the present disclosure showing an automatically generatedzone group consisting of two new zones;

FIG. 12 depicts a zone group manager in accordance with an exemplaryembodiment of the present disclosure showing a zone rejoined to itsoriginal zone group;

FIG. 13 is a flow chart illustrating a method of HVAC system deviceconfiguration in accordance with an exemplary embodiment of the presentdisclosure;

FIG. 14 is a flow chart illustrating a method of HVAC zone groupmanagement in accordance with an exemplary embodiment of the presentdisclosure;

FIG. 15 is a data architecture diagram of an HVAC system deviceconfigurator in accordance with an exemplary embodiment of the presentdisclosure;

FIGS. 16A and 16B are a data architecture diagram of an HVAC zone groupmanager in accordance with an exemplary embodiment of the presentdisclosure; and

FIG. 17 is block diagram of an exemplary embodiment of an HVAC design,modeling, and simulation system in accordance with the presentdisclosure.

The various aspects of the present disclosure mentioned above aredescribed in further detail with reference to the aforementioned figuresand the following detailed description of exemplary embodiments.

DETAILED DESCRIPTION

Particular illustrative embodiments of the present disclosure aredescribed hereinbelow with reference to the accompanying drawings;however, the disclosed embodiments are merely examples of thedisclosure, which may be embodied in various forms. Well-known functionsor constructions and repetitive matter are not described in detail toavoid obscuring the present disclosure in unnecessary or redundantdetail. Therefore, specific structural and functional details disclosedherein are not to be interpreted as limiting, but merely as a basis forthe claims and as a representative basis for teaching one skilled in theart to variously employ the present disclosure in any appropriatelydetailed structure. In this description, as well as in the drawings,like-referenced numbers represent elements which may perform the same,similar, or equivalent functions. The word “exemplary” is used herein tomean “serving as a non-limiting example, instance, or illustration.” Anyembodiment described herein as “exemplary” is not necessarily to beconstrued as preferred or advantageous over other embodiments. The word“example” may be used interchangeably with the term “exemplary.”

Aspects of the present disclosure are described herein in terms offunctional block components and various processing steps. It should beappreciated that such functional blocks configured to perform thespecified functions may be embodied in mechanical devices,electromechanical devices, analog circuitry, digital circuitry, and/ormodules embodied in a computer. It should be appreciated that theparticular implementations described herein are illustrative of thedisclosure and its best mode and are not intended to otherwise limit thescope of the present disclosure in any way. One skilled in the art willalso appreciate that, for security reasons, any element of the presentdisclosure may consist of any combination of databases or components ata single location or at multiple locations, wherein each database orsystem includes any of various suitable security features, such asfirewalls, access codes, authentication, encryption, de-encryption,compression, decompression, and/or the like. It should be understoodthat the steps recited herein may be executed in any order and are notlimited to the order presented. Moreover, two or more steps or actionsrecited herein may be performed concurrently.

The present disclosure is directed to methods and systems for designingand modeling an HVAC system of a structure. The system employs arules-based HVAC system schematic generator which enables a user toselect from among a number of predefined HVAC system configurations.Each systems configuration includes a plurality of HVAC components(“stencils”) each having a set of rules defining the component'sbehavior, and descriptors defining the interconnect circuits(electrical, fluid, control) between components. The selectedconfiguration is presented in schematic form to the user where it may bemodified by the user as needed, to add, delete, or reposition specificHVAC components in the system configuration. As new components areselected, the predefined rules for each component are applied to theschematic to determine one or more candidate positions at which theselected component may be inserted into the configuration. An updatedschematic showing the candidate positions for the new component isautomatically generated and displayed. When a user places the newcomponent in one of the candidate positions, the rules for eachcomponent and the interconnects are re-applied to the schematic and theschematic is again updated to reflect the new configuration. The newconfiguration may be added to the predefined HVAC system configurations.

A building may include one or more different HVAC system configurations.For example, a typical structure includes numerous climate control zones(rooms) having common system configurations, such as offices, conferencerooms, warehouses, and so forth. The system includes a hierarchic zoneassignment manager that organizes zones into zone groups, e.g., officezone group, conference room zone group, warehouse zone group. In thezone assignment manager the zones are presented as an architecturaldiagram of the structure, such as a 2D floor plan. For clarity, eachzone group is represented using distinct visual characteristics (e.g.,each zone has a different color, hatch pattern, background image, etc.)Each zone's system configuration is editable from within the zoneassignment manager, which enables a user to rapidly generate derivativeor alternative system configurations. In an example building, an officezone may consist of a VAV box, a temperature sensor, and associated HVACcomponents. However, certain offices in the example building havenorth-facing windows that cause additional heat loss, necessitating theaddition of a convector to the system configuration to properly heatthese north-facing offices. The system enables a user to select a roomand modify the associated zone as needed (e.g., add a convector) whichimmediately 1) creates a new zone group associated with the new systemconfiguration 2) removes the modified zone from its original zone group,and 3) joins the modified zone to the new zone group.

The disclosed system includes a simulation engine to evaluate theperformance of the system, which, together with the rules-based systemschematic generator and hierarchical zone manager, enables the designengineer to rapidly prototype, evaluate, and revise HVAC system designs.

Turning to FIG. 1, a graphic display 100 presents a set of systemconfiguration selection icons 101-104 representative of a predefinedsystem HVAC system configuration. In FIG. 2, a system configuration hasbeen selected and the core elements of the configuration are rendered inschematic form 105. In FIG. 3 a selection is made to add a cooling coil106. The rules-based engine processed the predefined rules for coolingcoil 106 to determine the candidate position(s) available for a coolingcoil 106, which is indicated by position icon 107. The placement ofcooling coil 106 to the system configuration is accomplished by draggingcooling coil 106 to the desired position 107. Immediately upon placementthe rules based engine updates schematic 105 to show cooling coil 108 inthe specified position (FIG. 4). The design engineer may elect to makefurther modifications, for example, to add a central water source heatpump (WSHP) unit or a variable speed supply fan 109. In this case thedesigner selects variable speed drive (VSD) supply fan 109 which againinvokes the rules based engine, which, in turn, generates position icons110 to indicate candidate positions for a VSD supply fan 109.

FIGS. 5-7 illustrate the steps of automatically configure controlelements and HVAC elements in context of the overall systemconfiguration as control elements are added to the system configuration.In FIG. 5 a VFD supply fan 113 a and a VAV reheat box (VRH) 113 b havebeen added to schematic 105. A selection is made to add a temperaturecontroller 112 and candidate placements 114 are displayed. In FIG. 6 thedesign engineer drags temperature controller tile 112 to the desiredposition, which immediately invokes the rules-based engine to add newtemperature controller 115 to schematic 105. The rules-based engineprocesses rules for each component of the system configuration, whetherthe component is existing or newly-added, to ensure, at all times that acorrect and valid system configuration is being developed. For example,here, the control circuit 116 necessary to communicatively coupletemperature controller 115 and system controller 117 is automaticallygenerated. Additional control lines 18 may be defined by the designengineer as shown in FIG. 7.

FIGS. 8-13 illustrate an exemplary embodiment of a hierarchic zonemanager 200 in accordance with the present disclosure. An initial zonehierarchy 201 is automatically created by zone management logic, basedon a zone-HVAC system association to identify zones with commoncomponents which are operatively associated with the particular HVACsystem under development. Note that a single building may incorporateone or more HVAC systems. As seen in FIG. 8, VRH-1 (202) represents VAVboxes with reheat coils which is shared by each zone of Zone Group 00(215) displayed in the hierarchy. Zone Group 00 (215) is associated witha single HVAC system configuration, and each zone listed in thehierarchy 201 corresponds to a zone shown on floor plan 203. Forclarity, floor plan 203 depicts all zones that currently use the samezone level equipment using the same color.

To add a zone-level component to a zone (e.g., add a component to aparticular room), the component to be added is selected. Here, forexample, VAV terminal 204 is being added. The zone to which thecomponent will be added, Zone 00-01 (205) is also selected. As shown inFIG. 9, zone selection may be performed by selecting the target zone inthe hierarchy (205) to reveal an edit icon 207 associated with thehierarchical listing or, alternatively, by selecting the target zone inthe floor plan (206) to reveal an edit icon 208 associated with the zonegraphic in floor plan 203. Clicking on either edit icon 207 or 208enables the design engineer to add, delete, or modify the component(s)on the selected zone 205.

After zone modification is complete, the zone management logic attemptsto identify an existing zone group which shares the characteristics ofthe just-modified Zone 00-01 (205). If one exists, the modified zone isremoved from its original zone group and added to the identified zonegroup. No such zone group exists, so a new zone group is automaticallycreated. As shown in FIG. 10, Zone 00-01 has been modified therefore isremoved from Zone Group 00 (210) and moved into new Zone Group 01 (211).A new zone group name “Zone Group 01” is automatically generated toidentify the newly-created zone group within the hierarchy. Floor plan203 is updated to show the new zone group in the floor plan (206) in adistinct visual format from other zone groups (e.g., different color,hatching, background photograph, etc.).

FIG. 11 illustrates the automatic creation of a new zone group 214 wheremultiple zones have been modified. Zones 212 and 213 are moved from ZoneGroup 00 (215) to newly-created Zone Group 02 (214) resulting from theaddition of a wall convector to each of those zones. In FIG. 12, zone212 is modified a second time to remove the wall convector. In response,the zone management logic moves Zone 00-03 (212) from Zone Group 02 backto Zone Group 00.

FIG. 13 illustrates a method of rules-based HVAC schematic generation300 in accordance with an exemplary embodiment of the presentdisclosure. In the step 305 an initial user interface consisting ofdevice templates (stencils), configuration (plant) templates, and aschematic workspace is generated by a presentation layer. Devicetemplates may include terminal devices (e.g., VAV boxes), systemcomponents (e.g., cooling coils), control devices (e.g., temperaturecontrollers), and/or any component suitable for use in an HVAC system.In the step 310, one or more HVAC components, control devices, and/orterminal devices are selected from a system or plant template. In thestep 315, a rules-based engine is invoked to run a rule set for theselected elements to ensure compliance with acceptable HVAC engineeringpractice and error checking. In step 320 the necessary rules areretrieved from a rules database. Each template has a uniquestencil-shaped part name and identifier. A specially-developed XML fileincludes predefined rules for each stencil. Each stencil includes amapping of a stencil to configuration and placement candidate locationsfor that specific configuration. A maximum device count for each stencilmay be included to limit the number of instances a particular device mayappear in the schematic or building. Performance and business rules(cost, energy efficiency etc.) which may be utilized by the simulationengine for each stencil are stored in database in XML form.

In the step 325 the appropriate rules are retrieved from the databaseand evaluated in the step 330 to determine which, if any, availablelocations exist at which to place the device template selected in thestep 310. If no locations are available, then in step 335 no candidatelocations are indicated on the schematic, and, additionally oralternatively, a message is generated to inform the user the selectedtemplate may not be used. Otherwise, if candidate locations exist, inthe step 340 the candidate locations are indicated on the schematic. Inthe step 345, the location at which to place the device template isselected. In the step 350, a set of performance and business rules areapplied to the schematic. In some instances, depending on applicableperformance and business rules, one or more components may becomeunavailable for use in the current configuration. In this case, anindication that certain components are now unavailable is generated(e.g., greyed-out icon, alert box message, etc.). In the step 355, theselected device template is placed in the user-specified location, andany necessary connections (fluid, power, control) are automaticallygenerated and displayed in the schematic.

FIG. 14 illustrates a method of zone group management 400 in accordancewith an exemplary embodiment of the present disclosure. The methodbegins with the step 405 wherein the initial zone hierarchy isdisplayed. The zone hierarchy may be displayed in a list form withexpandable/collapsible elements and in a floor plan form showing theroom/zone association. In the step 415 a zone from which a component isto be added, deleted, or have a component property modified, isselected. In step 420, a specially-developed XML file that includespredefined rules for each component is retrieved. Each component isrepresented by a template that maps the component to configuration andplacement candidate locations for the zone configuration. A maximumdevice count for each may be included to limit the number of instances aparticular device may appear in the schematic or building. Performanceand business rules (cost, energy efficiency etc.) which may be utilizedby the simulation engine are stored in database in XML form. In the step425, a device template to be added or deleted from the desired zone isselected, and in the step 430, an attempt is made to match the selecteddevice template to the set of devices in the selected zone. If no matchis identified, then in the step 435 no icon is displayed and/or an errormessage is displayed. Otherwise, a match is identified and in the step440 the selected change is applied to the zone, e.g., the devicetemplate selected in step 425 is added or deleted to the zone. In thesteps 450 and 455, zone management logic determines if the modified zonehas the same set of devices (same control, terminal, and systemcomponents) as that of another member of the zone group. If it does, inthe step 460 no change is made to the zone group. Otherwise, in the step465 if the modified zone includes a dissimilar set of devices, then anattempt is made to identify another zone group which shares the same setof devices as the modified zone. If such as zone group is found, themodified zone is moved to that zone group. If no such zone group exists,one is created and the modified zone is moved into the newly-createdzone.

FIG. 15 illustrates a data architecture of a schematic systemconfigurator 500 in accordance with an exemplary embodiment of thepresent disclosure that includes a presentation layer 510, a rules layer520, and a data access layer 530. FIG. 16 illustrates a dataarchitecture of a zone group manager 600 that includes a presentationlayer 610, a rules layer 620, a data access layer 630, and zone groupanalysis engine 640.

FIG. 17 depicts an exemplary embodiment of a system 700 for designing,modeling, and simulation of an HVAC system in accordance with thepresent disclosure. System 700 includes a computing device 705 having inoperative communication a processor 710, a memory 720, and storage 730.Computing device 705 can include, for example, a laptop computer, adesktop computer, or a mobile device (e.g., a mobile phone, a personaldigital assistant, etc.), or any other type of computing device now orin the future known. Memory 720 includes RAM memory which can be used,for example, for storage of transient data, computed and intermediateresults, I/O buffering, graphical user interface (GUI) buffering, andfor software program execution.

Storage 730 comprises non-volatile storage such as a NAND flash drive,EEPROM, ROM, magnetic hard disk, solid state disk (SSD), hybrid drives(combination hard disk/SSD) which can be used for storage of a datawhich persists through power cycling. Computing device 705 includes userinterface 740 that enables a design engineer to interact with the system700. User interface 740 may include a keyboard, pointing device,touchscreen, speech recognition, gesture-based interface, or other inputdevice that receives user inputs, such inputting or downloading buildingfloor plans; selection of HVAC system configurations, components, andcontrol devices; defining and modifying characteristics of zones andzone groups; and other user inputs relating to the various other aspectsof the present disclosure. User interface 740 includes one or morevisual displays, which may include, without limitation, a monitor screenor monitor interface, browser interface, a virtual graphics outputdevice, and a remote access interface.

Computing device 705 includes a communications interface 750 forcommunication between system 700 and other systems and devices to enablereceiving and transmitting data in connection with aspects of thepresent disclosure, for example, downloading building floor plans,receiving updates relating to system configurations, HVAC components,rules updates, software updates, communication of design, modeling, andsimulation data, climate data, error logging and reporting, and soforth.

Still referring to FIG. 17, system 700 includes presentation layer 760,rules engine 700, logic engine 780, and database 790. Presentation layer760 interacts with user interface 740 to interpret user inputs, formatand present visual representations of schematics, floor plans,templates, stencils, icons and other visual elements of the disclosedinvention. Presentation layer 760 may include executable datapresentation software such Windows Presentation Foundation, Nevron, andthe like. Rules engine 770 interprets and processes rules-based criteriain connection with the schematic system configurator and zone groupmanagement. Logic engine 780 receives and transmits data to and frompresentation layer 760, rules engine 770, and database 790 to facilitateoperation of the disclosed invention, including without limitation, theanalysis, matching and creation of zone groups. Database 790 includes arelational database such as SQL Server for efficient storage andretrieval of data relating to the operation of the disclosed invention,such as without limitation, XML templates, rules, zone configurations,and so forth.

Aspects

It is noted that any of aspects 1-17 may be combined with each other inany combination

Aspect 1. A method for constructing an HVAC system for a structurehaving distinct thermal zones, comprising the steps of defining thestructure; defining an HVAC topology included in the structure;identifying common elements of the HVAC topology associated with adistinct thermal zone; defining a zone group comprising distinct zonessharing similar common elements; modifying the zone group if at leastone distinct zone of the zone group no longer shares common elementswith at least one other distinct zone of the zone group; generating aset of HVAC parameters for the structure.

Aspect 2. The method in accordance with aspect 1, wherein the step ofdefining an HVAC topology included in the structure comprises definingone or more HVAC components included in the structure.

Aspect 3. The method in accordance with any of aspects 1-2, wherein thestep of defining an HVAC topology included in the structure comprisesdefining an interconnection between one or more HVAC components includedin the structure.

Aspect 4. The method in accordance with any of aspects 1-3, wherein thestep of modifying the zone group comprises removing from the zone groupthe distinct zone that no longer shares common elements with at leastone other distinct zone of the zone group; and adding the removeddistinct zone to a different zone group comprising distinct zonessharing similar common elements with the removed distinct zone.

Aspect 5. The method in accordance with any of aspects 1-4, whereindefining an HVAC topology included in the structure comprises providinga set of pre-defined characteristics of an HVAC component, wherein thepre-defined characteristics include a configuration rule and asimulation rule; inserting a representation of a distinct thermal zoneinto a zone tree; joining the HVAC component to at least one other HVACcomponent in the distinct thermal zone, if any, based upon thepre-defined characteristics of the respective HVAC components.

Aspect 6. The method in accordance with any of aspects 1-5, wherein theset of pre-defined characteristics of an HVAC component are expressed inan extensible markup language.

Aspect 7. The method in accordance with any of aspects 1-6, whereininserting the representation into a zone tree representative of adistinct thermal zone includes storing the configuration rule and thesimulation rule in third normal form.

Aspect 8. A method for constructing an HVAC system model of a structurehaving distinct thermal zones, comprising the steps of defining thestructure; defining a plurality of HVAC components included in thestructure; defining interconnections between two or more of theplurality of HVAC components included in the structure; identifying afurther HVAC component to be inserted into an interconnection of thestructure; and identifying a candidate interconnection into which thefurther HVAC component may be inserted.

Aspect 9. A method, comprising displaying a plurality of HVAC systemconfigurations in a viewer executing on an electronic device having agraphic display;

receiving, at the electronic device, a user selection of HVAC systemconfiguration displaying the selected HVAC system configuration in theviewer displaying a plurality of HVAC components in the viewerreceiving, at the electronic device, a user selection of a HVACcomponent applying a rules-based engine to determine the possiblelocations within the HVAC system configuration where the selected HVACcomponent may be placed; and displaying the possible locations theselected HVAC component may be placed on the HVAC system configurationin the viewer.

Aspect 10. A computer-implemented method for configuring a heating,ventilation, and air conditioning (HVAC) system of a building,comprising receiving, by a processor, a floor plan of the building;receiving, by the processor, an HVAC system configuration selected fromamong a set of template HVAC configurations; receiving, by theprocessor, an HVAC component selected from among a set of template HVACcomponents; determining, by the processor, a candidate position for theHVAC component within the HVAC system configuration; and displaying, ona visual display in communication with the processor; the candidateposition for the HVAC component on a schematic diagram of the HVACsystem configuration.

Aspect 11. A computer-implemented method for configuring a heating,ventilation, and air conditioning (HVAC) system of a building,comprising receiving, by a processor, a floor plan of the building,wherein the floor plan includes a mapping of an HVAC systemconfiguration to a first HVAC zone group; receiving, by the processor, achange to the HVAC system configuration associated with a first HVACzone of the first HVAC zone group; determining, by the processor,whether a second HVAC zone group is mapped to a system configurationhaving the same properties as the changed HVAC configuration of thefirst zone.

Aspect 12. The computer-implemented method in accordance with aspect 11,further comprising responding to a determining that a second HVAC zonegroup is mapped to a system configuration having the same properties asthe changed HVAC configuration of the first zone by removing the firstzone from the first HVAC zone group and adding the first zone to thesecond HVAC zone group.

Aspect 13. The computer-implemented method in accordance with any ofaspects 11-12, further comprising responding to a determining that asecond HVAC zone group is not mapped to a system configuration havingthe same properties as the changed HVAC configuration of the first zoneby removing the first zone from the first HVAC zone group, creating anew HVAC zone group, and adding the first zone to the new HVAC zonegroup.

Aspect 14. The computer-implemented method in accordance with any ofaspects 11-13, further comprising automatically assigning a new name tothe new HVAC zone group.

Aspect 15. The computer-implemented method in accordance with any ofaspects 11-14, further comprising displaying, on a visual display incommunication with the processor; zone of the new zone group using adifferent visual representation from that of the first zone group.

Aspect 16. The computer-implemented method in accordance with any ofaspects 11-15, wherein a different visual representation includes adifferent color, a different hatching, and/or a different backgroundimage.

Aspect 17. A system as substantially described herein.

Particular embodiments of the present disclosure have been describedherein, however, it is to be understood that the disclosed embodimentsare merely examples of the disclosure, which may be embodied in variousforms. Well-known functions or constructions are not described in detailto avoid obscuring the present disclosure in unnecessary detail.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but merely as a basis for theclaims and as a representative basis for teaching one skilled in the artto variously employ the present disclosure in any appropriately detailedstructure.

1-19. (canceled)
 20. A device for constructing an HVAC system for astructure having distinct thermal zones, comprising: a processor; and amemory operatively coupled to the processor and storing instructions,which, when executed by the processor, cause the device to: define thestructure; define an HVAC topology included in the structure; identifycommon elements of the HVAC topology associated with a distinct thermalzone; define a zone group comprising distinct zones sharing a commonelement; modify membership of the zone group in response to adetermination that a first zone of the zone group no longer shares thecommon element with a second zone of the zone group; and determine adifferent common element shared by the first zone.
 21. The device inaccordance with claim 20, wherein the memory further storesinstructions, which, when executed by the processor, cause the device todefine one or more HVAC components included in the structure.
 22. Thedevice in accordance with claim 20, wherein the memory further storesinstructions, which, when executed by the processor, cause the device todefine an interconnection between one or more HVAC components includedin the structure.
 23. The device in accordance with claim 20, whereinthe memory further stores instructions, which, when executed by theprocessor, cause the device to remove from the zone group the first zonethat no longer shares the common element with the second zone of thezone group; and add the first zone to a different zone group comprisingdistinct zones sharing the different common element.
 24. The device inaccordance with claim 20, wherein the memory further storesinstructions, which, when executed by the processor, cause the deviceto: provide a set of pre-defined characteristics of an HVAC component,wherein the pre-defined characteristics include a configuration rule anda simulation rule; insert a representation of a distinct thermal zoneinto a zone tree; join the HVAC component to at least one other HVACcomponent in the representation of the distinct thermal zone based uponthe pre-defined characteristics of the respective HVAC components beingjoined.
 25. The device in accordance with claim 24, wherein the set ofpre-defined characteristics of an HVAC component is expressed in anextensible markup language.
 26. The device in accordance with claim 24,wherein the memory further stores instructions, which, when executed bythe processor, cause the device to store the configuration rule and thesimulation rule in third normal form.
 27. A device for constructing anHVAC system for a structure having distinct thermal zones, comprising: aprocessor; and a memory operatively coupled to the processor and storinginstructions, which, when executed by the processor, cause the deviceto: define the structure; define a plurality of HVAC components includedin the structure; define interconnections between two or more of theplurality of HVAC components included in the structure; identify afurther HVAC component to be inserted into an interconnection of thestructure; and identify a candidate interconnection into which thefurther HVAC component may be inserted.
 28. The device in accordancewith claim 27, wherein the memory further stores instructions, which,when executed by the processor, cause the device to insert the furtherHVAC component into the candidate interconnection.
 29. The device inaccordance with claim 27, wherein the memory further storesinstructions, which, when executed by the processor, cause the device toselect the candidate interconnection from the group consisting of arefrigerant circuit, an air duct, and a control circuit.
 30. A device,comprising: a processor; a graphic display operatively coupled to theprocessor; and a memory operatively coupled to the processor and storinginstructions, which, when executed by the processor, cause the deviceto: display a plurality of HVAC system configurations on the graphicdisplay; receive a user selection of HVAC system configuration; displaythe selected HVAC system configuration on the graphic display; display aplurality of HVAC components on the graphic display; receive a userselection of a HVAC component; apply a rules-based engine to determinethe possible locations within the HVAC system configuration at which theselected HVAC component may be placed; and display the possiblelocations the selected HVAC component may be placed on the HVAC systemconfiguration on the graphic display.
 31. The device in accordance withclaim 30, wherein the memory further stores instructions, which, whenexecuted by the processor, cause the device to place the selected HVACcomponent at one of the determined possible locations.
 32. A device forconfiguring a heating, ventilation, and air conditioning (HVAC) systemof a building, comprising: a processor; a graphic display operativelycoupled to the processor; and a memory operatively coupled to theprocessor and storing instructions, which, when executed by theprocessor, cause the device to: receive a floor plan of the building;receive an HVAC system configuration selected from among a set oftemplate HVAC configurations; receive an HVAC component selected fromamong a set of template HVAC components; determine a candidate positionfor the HVAC component within the HVAC system configuration; display aschematic diagram of the HVAC system configuration on the graphicdisplay; and display the candidate position for the HVAC component onthe schematic diagram.
 33. A device for configuring a heating,ventilation, and air conditioning (HVAC) system of a building,comprising: a processor; a graphic display operatively coupled to theprocessor; and a memory operatively coupled to the processor and storinginstructions, which, when executed by the processor, cause the deviceto: receive a floor plan of the building, wherein the floor planincludes a mapping of an HVAC system configuration to a first HVAC zonegroup; receive a change to the HVAC system configuration associated witha first HVAC zone of the first HVAC zone group; determine whether asecond HVAC zone group is mapped to a system configuration having thesame properties as the changed HVAC configuration of the first zone;respond to a determining that a second HVAC zone group is not mapped toa system configuration having the same properties as the changed HVACconfiguration of the first zone by removing the first zone from thefirst HVAC zone group, creating a new HVAC zone group, and adding thefirst zone to the new HVAC zone group; and displaying, on the graphicdisplay, the zone of the new zone group using a different visualrepresentation from that of the first zone group.
 34. The device inaccordance with claim 33, wherein the memory further storesinstructions, which, when executed by the processor, cause the device torespond to a determining that a second HVAC zone group is mapped to asystem configuration having the same properties as the changed HVACconfiguration of the first zone by removing the first zone from thefirst HVAC zone group and adding the first zone to the second HVAC zonegroup.
 35. The device in accordance with claim 33, wherein the memoryfurther stores instructions, which, when executed by the processor,cause the device to automatically assign a new name to the new HVAC zonegroup.
 36. The device in accordance with claim 33, wherein the differentvisual representation includes a different color, a different hatching,and/or a different background image.